Gradio SDK 5.31.0 fully dysfunctional API on Huggingface

Hi, it seems there is a massive problem with gradio and huggy:

Tested, fixed and not working:
:white_check_mark: API endpoint diagnostics - tested various URLs
:white_check_mark: Gradio versions synchronized - version conflicts found
:white_check_mark: Code bugs fixed - detailed undefined, headers undefined
:white_check_mark: FastAPI vs. Gradio separated - mount conflicts resolved
:white_check_mark: Gradio client tested - space-to-space communication
:white_check_mark: React integration - various API formats
:white_check_mark: Finally: HuggingFace infrastructure issue identified

results
All Gradio APIs are listed below:

:cross_mark: /api/predict → 404
:cross_mark: /queue/join → 405
:cross_mark: Gradio Client → 405
:cross_mark: Space-to-Space → 404

I know Gradio can be a diva, but this is something that we should definitely have a look at. What am I doing wrong? problem is, when I try to use a stable gradio like 4.44 or 5.8 in requirements.txt, the HF environment always sets it back to the bug machine 5.31.0

1 Like

Hmm… I think it’s just a bug. It doesn’t seem to have been reported as an issue, though.

There’s also a bug in the ImageEditor component in 5.31.0, so I reverted back to 5.29.1

1 Like

Thank you for clarification. Problem 2, the FastAPI + Gradio Mount Bug in 5.31.0 hits my problem like :bullseye::bullseye: Okay that’s bad for now but stuff happens and at least I know now that I’m not missing something. Thank you for your helpful resonse! I’ll keep everyone updated in case I find a way to work around it.

1 Like